System and method for managing multimedia messaging platforms

ABSTRACT

The present invention manages a messaging network having messaging platforms interconnecting through a switched backbone such as the Internet. The master platform monitors each messaging platform on the messaging network and administers the addition, deletion, and updating of messaging platforms by modifying a master global routing table in the event the master platform encounters changes to the status of the messaging platforms. In the event that the master global routing table is updated, the global routing table held at each messaging platform is also updated, ensuring version consistency between said master global routing table and each of the global routing tables. This enables the master platform and each messaging platform to determine the operational status of another messaging platform. The present invention may also provide a cost tracking scheme when delivering messages between messaging platforms that are owned by different entities. This avoids use agreements between messaging platform owners and owners of networks which are connected to the messaging platforms. The cost for each network message delivery is measured in tokens. The present invention may also include a post office function that enables a master platform to receive and store a status message destined for a messaging platform which does not have an active connection to the messaging network or is in a non-operational state. The present invention may also include an information delivery service that delivers a message from at least one source outside of the messaging network to a subscriber via the subscriber&#39;s messaging platform regardless of whether the messaging platform has a dedicated or dial-up connection.

CROSS REFERENCES TO RELATED APPLICATIONS

[0001] This application is a continuation-in-part of co-pending U.S.patent application Ser. No. 08/853,290 filed May 9, 1997, entitled,“APPARATUS AND METHOD FOR PROVIDING MULTIMEDIA MESSAGING BETWEENDISPARATE MESSAGING PLATFORMS.” The complete disclosure of the foregoingpatent application is hereby incorporated herein by reference as if setforth fully herein.

BACKGROUND OF THE INVENTION

[0002] 1. Field of the Invention

[0003] This invention relates to the management of messaging platformsthat are interconnected to form a wide-area network.

[0004] 2. Background

[0005] A messaging system as shown in U.S. Pat. No. 5,568,540 to Grecoet. al., enables a user to receive messages having a voice mail formateither through a telephone or through a personal computer (“PC”) coupledto a local area network (LAN). It also provides a graphical userinterface (“GUI”) on the PC to select which voice mail messages toreceive and in what order. However, the messaging system in Greco is astand-alone system and thus, does not provide the advantages of linkingto other similar messaging systems or of using interconnected messagingsystems to provide distributed messaging.

[0006] Accordingly, it would be desirable to integrate messagingplatforms distributed on a switchable communications backbone such asthe Internet, or equivalent network such as a wide area corporateintranet, and connected to different area networks so as to provideglobal yet low cost messaging.

[0007] Moreover, it would be desirable to monitor each messagingplatform and administer the addition, deletion, and updating of amessaging platform in response to a status change to the messagingplatform so that each messaging platform is aware of the status change.

[0008] In addition, it would be desirable to minimize the complexitythat would result if every independent owner of a messaging platform hadto contract with every other independent owner of a messaging platformin order to deliver a message within a certain service area served by amessaging platform by imposing a cost tracking scheme on each messagingplatform that uses the switched backbone to send a message to anothermessaging platform for delivery to the service area.

[0009] Furthermore, it would be desirable to provide a feature thatmanages a status message destined for a messaging platform which doesnot have an active connection to the switched backbone so that thestatus message is promptly delivered to the messaging platform the nexttime it re-establishes a connection to the switched network and resultsin a message confirming delivery of the status message to the messagingplatform.

[0010] Last, it would be desirable to include an information deliveryservice that delivers a message from at least one source outside of themessaging network to a subscriber via the subscriber's messagingplatform regardless of whether the messaging platform has a dedicated ordial-up connection.

SUMMARY OF THE INVENTION

[0011] The present invention manages a messaging network havingmessaging platforms interconnecting through a switched backbone such asthe Internet. Each messaging platform may be independently owned and mayalso connect to local networks that may be independently owned. A masterplatform maintains a master global routing table having a messagingplatform profile for every messaging platform established on themessaging network. Each messaging platform holds a global routing tablewhich includes a current version of the master global routing table. Themaster platform monitors each messaging platform on the messagingnetwork and administers the addition, deletion, and updating ofmessaging platforms by modifying its master global routing table in theevent the master platform encounters changes to the status of themessaging platforms. In the event that the master global routing tableis updated, the global routing table held by each messaging platform isalso updated, ensuring version consistency between the master globalrouting table and each of the global routing tables. This enables themaster platform and each messaging platform to determine the operationalstatus of another messaging platform.

[0012] Also, since the messaging platforms may be independently ownedand are designed to receive and deliver messages through a variety ofnetworks that may impose surcharges, the present invention also providesa cost tracking feature when delivering messages between messagingplatforms that are owned by different entities. This avoids the need foruse agreements between messaging platform owners and owners of networkswhich are connected to the messaging platforms. The cost for eachnetwork message delivery is measured in tokens. Each messaging platformon the messaging network has a token pool. Each owner of a messagingplatform is charged for the cost of the tokens. Each time a networkmessage delivery is initiated, the originating messaging platform debitsa selected number of tokens from its token pool, while each time aninbound network message delivery occurs, a selected number of tokens arecredited to the token pool held by a target messaging platform.

[0013] The present invention also includes a post office function thatenables a master platform to receive and store a status message destinedfor a messaging platform which does not have an active connection to themessaging network or is in a non-operational state. The presentinvention also includes an information delivery service that delivers amessage from at least one source outside of the messaging network to asubscriber via the subscriber's messaging platform regardless of whetherthe messaging platform has a dedicated or dial-up connection.

BRIEF DESCRIPTION OF THE DRAWINGS

[0014]FIG. 1 is a schematic block diagram of a messaging managementsystem in a presently preferred embodiment of the present invention.

[0015]FIG. 2A is a block diagram of a global routing table in accordancewith a preferred embodiment of the present invention.

[0016]FIG. 2B is a block diagram of a local area routing table inaccordance with a preferred embodiment of the present invention.

[0017]FIG. 3 is a block diagram showing the addition of a messagingplatform to the messaging network in accordance with a preferredembodiment of the present invention.

[0018]FIG. 4 is a flow chart of the steps taken by a master platformwhen monitoring messaging platforms on the messaging network inaccordance with a preferred embodiment of the present invention.

[0019]FIG. 5 is a flow chart of the steps taken by a messaging platformas part of the monitoring of the network by a master platform inaccordance with a preferred embodiment of the present invention.

[0020]FIG. 6A is a block diagram showing the deactivation of a messagingplatform in accordance with a preferred embodiment of the presentinvention.

[0021]FIG. 6B is a block diagram showing the activation of a messagingplatform in accordance with a preferred embodiment of the presentinvention.

[0022]FIG. 6C is a block diagram showing the deletion of a messagingplatform in accordance with a preferred embodiment of the presentinvention.

[0023]FIG. 7 is a schematic block diagram of a messaging managementsystem having a post office feature in accordance with a preferredembodiment of the present invention.

[0024]FIG. 8 is a block diagram showing the delivery of information froman information source to a mailbox corresponding to a subscriber inaccordance with a preferred embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0025] In the following description, a preferred embodiment of theinvention is described with regard to preferred process steps and datastructures. Those skilled in the art would recognize after perusal ofthis application that embodiments of the invention can be implementedusing circuitry in a microprocessor adapted to the particular processsteps and data structures, and that implementation of the process stepsand data structures described herein would not require undueexperimentation or further invention.

[0026] The present invention may be used with co-pending U.S. patentapplication Ser. No. 08/853,290 filed May 9, 1997, entitled, “APPARATUSAND METHOD FOR PROVIDING MULTIMEDIA MESSAGING BETWEEN DISPARATEMESSAGING PLATFORMS,” hereinafter referred to as the (“multimediamessaging invention”). The complete disclosure of the foregoing patentapplication is hereby incorporated herein by reference as if set forthfully herein.

[0027] To further enhance the description of the various features of thepresent invention, “Service Communication Platform,” Release 2.0,available from Carnel Connection, Inc. located at 41432 Christy Street,Fremont, Calif., 94538 is also incorporated herein by reference as ifset forth fully herein.

[0028]FIG. 1 is a schematic block diagram of a messaging managementsystem in a presently preferred embodiment of the present invention.

[0029] As seen in FIG. 1, a messaging network 10 enables a user 12 tosend or receive a message to or from another user 14 using themultimedia services provided by a messaging platform 16 connected tomessaging network 10. Messaging network 10 uses a switched backbone 18such as the Internet, enabling messaging platform 16 to send or receivemultimedia messages with another messaging platform on messaging network10 such as remote messaging platform 20. This provides global messagingat very low cost.

[0030] Besides the switched backbone 18, each messaging platform mayalso individually connect to local networks such as a public switchtelephone network 22, 24, 26 (PSTN) which may be connected to messagingdevices such as telephones 28, 30, 32 and/or fax machines 34, 36, 38; aprivate branch exchange 40, 42, 44 (PBX) which may also connect to amessaging device such as a telephone 46, 48, 50; or a privatelyadministered LAN and/or WAN 52, 54, 56 which may connect to messagingdevices that include a computer terminal 58, 60, 62 or personal computer64, 66, 68 running a browser program. These networks may be owned andoperated by an owner who may or may not be affiliated with an owner of amessaging platform.

[0031] The present invention manages messaging network 10 by monitoringthe current availability of each existing messaging platform andadministering the addition, deletion, and updating of messagingplatforms on messaging network 10. The master platforms and messagingplatforms described herewith contain a programmable control means suchas a microprocessor system running under program control or anequivalent device to perform these functions.

[0032] Also, since the messaging platforms may be independently ownedand are designed to receive and deliver messages through a variety ofnetworks that may impose surcharges, the present invention provides acost tracking scheme when delivering messages between messagingplatforms that are owned by different entities. This avoids the need forcomplex use agreements between messaging platform owners and owners ofnetworks which are connected to the messaging platforms.

[0033] In accordance with a presently preferred embodiment of thepresent invention, the messaging platforms on messaging network 10 aremanaged by at least one master platform 70. Every master platform on themessaging network 10 contain a master global routing table and everymessaging platform on the messaging network contains a global routingtable. Master platform 70 maintains a master global routing table 72 foran assigned group of messaging platforms, such as messaging platforms 16and 20, by editing a messaging platform entry within master globalrouting table 72 that corresponds to a messaging platform having astatus change. Master platform 70 maintains content consistency, througha microprocessor system running under program control or an equivalentdevice, between master global routing table 72 and global routing tables74 and 76 so that master platform 70 and messaging platforms 16 and 20each rely on the same messaging platform entries within the globalrouting tables.

[0034] In response to an applicable event such as the status changediscussed above, master platform 70 sends an UPDATE message to messagingplatforms 16 and 20, enabling messaging platforms 16 and 20 to updatetheir global routing tables 74 and 76 through a microprocessor systemrunning under program control or an equivalent device. As presentlycontemplated, the UPDATE message includes at least one messagingplatform entry that was modified by master platform 70. The messagingplatform entry is used by messaging platforms 16 and 20 to update acorresponding entry in their global routing tables 74 and 76,respectively.

[0035]FIG. 2A is a block diagram of a global routing table in accordancewith a preferred embodiment of the present invention.

[0036] A global routing table 80 as used in the present inventioncontains a corresponding messaging platform entry 82 for each messagingplatform on messaging network 10. Each messaging platform entry includesfields that may point to or include the following: a host ID 84; anoperational status 85; an operation schedule 86; a permanent InternetProtocol (IP) address 87 (if applicable); an area of operation 88, and atoken pool 89.

[0037] Host ID 84 is a unique identifier for every messaging platformadded to the messaging network. Host ID 84 may further includeadditional identifiers such as a domain name 90; a name recording file92; and/or a network address or equivalent 94.

[0038] Operational status 85 defines the operational state of amessaging platform as determined by the master platform assigned to themessaging platform. It is presently contemplated that operational status85 has either an in-operation (ACTIVATED) or a non-operational(DEACTIVATED) state. Changing the state of operation status 85 isfurther discussed below.

[0039] Operation schedule 86 defines the operation window for amessaging platform. Operation schedule 86 includes a daily operationperiod 96 and an hourly operation period 98. Daily operation period 96has a format that includes a start time and an end time in units ofhours that are separated by a dash. For example, a daily operationperiod that starts from 8 AM and ends at 6 PM would be indicated as“08-18.” Similarly, a round-the-clock operation would be indicated as“00-23.”

[0040] Hourly operation period 98 defines the hourly operation windowfor a messaging platform. Hourly operation period 98 has a format thatincludes a start time and an end time in units of minutes that areseparated by a dash. For example, an hourly operation period 98 thatstarts every fifteen minutes beyond the hour and ends at every half-hourwould be indicated as “15-30,” while full hourly operation would beindicated as “00-59.”

[0041] Domain name 90 defines a unique network name for messagingplatform that corresponds to the messaging platform entry. For amessaging platform that uses the Internet as its switched backbone,domain name 90 corresponds to a TCP/IP network address and complies withthe convention for naming a host node, such as a messaging platform, onthe Internet.

[0042] In the event that the messaging platform entry corresponds to amessaging platform having a dedicated connection to the switchedbackbone, permanent IP address field 87 contains a permanent IP addressor similar network address.

[0043] Area of operation 88 may be defined using a local network routingtable 100, which is a variable length table but could have any formatthat is suitable for storing a variable amount of information. The typeof information held by local network routing table 100 is dependent onthe type of local network connection that a particular messagingplatform is capable of supporting besides a messaging networkconnection. When a messaging platform is configured to also support atelephone network, a local network routing table that corresponds tothat messaging platform through its messaging platform entry wouldinclude a list of telephone number prefix digits. The telephone numberslisted in local network routing table 100 enable an originatingmessaging platform to determine which messaging platform can provideservice to those telephone numbers by cross-referencing a destinationtelephone number with the messaging platform entries in the originatingplatform's global routing table.

[0044] Token pool 89 has an initial value that may vary according to theamount sought by an owner of each new messaging platform added. The useof token pool 89 in the present invention will be further describedbelow.

[0045]FIG. 2B shows a local network routing table 101 having prefixdigits 102 which correspond to a list of telephone numbers. As presentlycontemplated, prefix digits 102 may include a country code 103 and areacode 104, or may further include an office digit code 106 to furtherdefine the range of numbers that can be called.

[0046] Local network routing table 101 enables an originating messagingplatform to determine which remote messaging platform is capable ofdelivering a user message at an area of operation. The originatingmessaging platform cross-references the user message address, which maybe in the form of a telephone number, with every local network routingtable contained in the messaging platform's global routing table.

[0047] For example, a fax originating from an originating messagingplatform in Hong Kong may have a fax destination number having a countrycode of “1” and an area code of “510”. The originating platformcross-references the fax number with its local network routing table todetermine which remote messaging platform on the messaging network canservice that country and area code. More specifically, originatingmessaging platform can then determine which messaging platform entry touse in order to obtain delivery information such as the domain name ofthe remote messaging platform and its hours of operation.

[0048] Returning to FIG. 2A, name recording file 92 contains a voicerecording of the name of a messaging platform. Name recording file 92may be in any suitable digitized file format such as a .WAV file orsimilar digitized audio file format.

[0049] Network address field 94 holds a permanent IP address, or anequivalent type of network address that is applicable to the type ofswitched backbone used, of a messaging platform if the messagingplatform has a permanent connection to the messaging network. Otherwise,network address field contains an indication that the messaging platformcorresponding to the messaging platform entry is configured for dialupconnection to the messaging network.

[0050] Adding Messaging Platforms

[0051]FIG. 3 is a process chart showing the addition of a messagingplatform to the messaging network in accordance with a preferredembodiment of the present invention.

[0052] Referring to FIGS. 1-3, at step 120 a the addition of a newmessaging platform 122 on messaging network 10 begins by requesting anadd operation from a system administrator 124 of master platform 70. Atstep 120 b, the add operation includes a registration process thatrequires system administrator 124 to receive registration information126 pertaining to new messaging platform 122. Registration information126 includes a preferred name 128, a permanent IP address 130 or anindication 132 whether new messaging platform 122 will have adynamically assigned IP address, a domain name 134 (if any), and aninitial token amount 136 to fill token pool 89.

[0053] Initial token amount 136 may vary among new messaging platformsadded to messaging network 10 according to the amount sought by theowner of each new messaging platform. Initial token amount 136 held by amessaging platform at any given time may be replenished through a masterplatform upon request, as will be described in detail below.

[0054] As additional sub-steps to step 120 b, a local network routingtable 138 and/or an operation schedule 140 may also be provided tosystem administrator 124.

[0055] At step 120 c, system administrator 124 creates a new messagingplatform entry 142 corresponding to new messaging platform 122 in masterglobal routing table 72. New messaging platform entry 142 includesregistration information 126 and a unique node ID 144.

[0056] As an additional sub-step in step 120 c, a name recording file146 may also be created by system administrator 124 and included withnew messaging platform entry 142 in master global routing table 72, ifthe new messaging platform is intended for connection to a telephonenetwork such as telephone network 26.

[0057] At step 120 d, once new message platform entry 142 has beencreated on master global routing table 72, a system administrator 148for new messaging platform 122 is provided configuration information 150which includes assigned node ID 144 and an IP address 152 of masterplatform 70. Configuration information 150 may also include a password154 that master platform 70 will recognize as unique to new messagingplatform 122.

[0058] At step 120 e, system administrator 148 configures new messagingplatform 122 to have configuration information 150.

[0059] At step 120 f, in response to entering configuration information150, new messaging platform 122 establishes a connection with masterplatform 70 using master platform IP address 152, enabling masterplatform 70 to respond by providing new messaging platform 122 withapplicable information.

[0060] More specifically at step 120 g, new messaging platform 122 sendsan installation request 156 which includes node ID 144, and a password154 if implemented, to master platform 70. Master platform 70 willrecognize node ID 144 as pertaining to new messaging platform 122 basedon corresponding messaging platform entry 142 in master global routingtable 72 and performs step 120 h.

[0061] At step 120 h, master platform 70 downloads a copy of masterglobal routing table 72 to new messaging platform 122.

[0062] At step 120 i, global routing tables 74 and 76 for messagingplatforms 16 and 20 on messaging network 10 are updated by masterplatform 70 to include a messaging entry corresponding to new messagingplatform 122. Master platform 70 sends an UPDATE message to messagingplatforms 16 and 20 which trigger messaging platforms 16 and 20 toinclude the new messaging platform entry in their global routing tables74 and 76, respectively.

[0063] Monitoring Messaging Platforms

[0064]FIG. 4 is a flow chart of the steps taken by a master platformwhen monitoring messaging platforms on the messaging network inaccordance with a preferred embodiment of the present invention.

[0065] Through a microprocessor system running under program control oran equivalent device, a master platform monitors its assigned messagingplatforms and updates its master global routing table in response to themonitoring function.

[0066] At step 160 a, a messaging platform sends a HELLO message to itsassigned master platform at selected intervals over a given timeschedule. For a messaging platform having a dedicated connection, theselected intervals may be at any selected interval such as everyhalf-hour on the half-hour, 24 hours each day. This selected interval of30 minutes may be varied and is not intended to limit the presentinvention in anyway. For a messaging platform having a dial-upconnection to the switched backbone, the messaging platform only sendsHELLO messages while having a messaging network connection and duringthe operation schedule defined by the messaging platform's daily andhourly operation periods.

[0067] As presently contemplated, a HELLO message includes a commandtype, node ID, and password (if applicable) that corresponds to thesending messaging platform. The HELLO message may also includeadditional information pertaining to the messaging platform such as itscurrent token pool balance.

[0068] At step 160 b, if the HELLO message from the messaging platformis not received by its assigned master platform within an amount of timeof the scheduled time (selected wait time) to receive the HELLO message,step 160 c is performed.

[0069] At step 160 c, the master platform will send a QUERY message tothe late messaging platform. It is presently contemplated that theselected wait time be no more than ten (10) minutes beyond the scheduledtime to receive a HELLO message.

[0070] A QUERY message includes a command type, a node ID, and password(if applicable) that corresponds to the sending messaging platform.

[0071] At step 160 d, if the late messaging platform does not respondwithin the selected wait time, step 160 e is performed. At step 160 e,the master platform changes the status of the non-responding messagingplatform to a non-operational status and alerts the master platformsystem administrator of the non-operational status of the non-respondingmessaging platform. In addition, the master platform returns to step 160c and sends another QUERY message to the late messaging platform with aselected wait time.

[0072] If at step 160 b, the assigned master platform receives a HELLOmessage from the messaging platform within the selected wait time, step100 f is performed. At step 100 f, the assigned master platform replieswith an acknowledge message (ACK).

[0073]FIG. 5 is a flow chart of the steps taken by a messaging platformas part of the monitoring of the network by a master platform inaccordance with a preferred embodiment of the present invention.

[0074] At step 162 a, if the HELLO message, which was sent by themessaging platform, is not responded to with an ACK message by themessaging platform's assigned master platform within a selected waittime, step 162 b is performed.

[0075] At step 162 b, the messaging platform sends another HELLOmessage. It is presently contemplated that the particular messagingplatform has a selected wait time of 10 minutes before sending anotherHELLO message. The amount of wait time is not considered to be limitingin anyway but may be varied to response to the processing loads incurredby a given master and messaging platform so as to optimize systemperformance.

[0076] At step 162 c, if the assigned master platform does not respondto the second HELLO message, step 162 d is performed. At step 162 d, themessaging platform may keep sending a HELLO message each time the waittime expires by returning to set 162 b. The messaging platform in step162 d may also send an alert message to the particular messagingplatform's system administrator.

[0077] Returning to step 162 a, if the HELLO message is responded towith an ACK by the master platform within a selected wait time, step 162e is performed. At step 162 e, the messaging platform sends anotherHELLO message to the master platform according to a schedule defined forthe messaging platform.

[0078] Similarly in step 162 c, if the assigned master platform doesrespond to the second HELLO message within a selected wait time, step160 e is performed so that the messaging platform sends another HELLOmessage according to a schedule defined for the messaging platform.

[0079] Activating/Deactivating a Messaging Platform

[0080]FIG. 6A is a block diagram showing the deactivation of a messagingplatform in accordance with a preferred embodiment of the presentinvention.

[0081] Referring to FIGS. 1 and 6A, in the event that a messagingplatform such as messaging platform 16 has a non-operational status forany significant amount of time, such as one hour, master platformadministrator 124 can choose to deactivate messaging platform 16 frommessaging network 10.

[0082] Deactivation includes the following steps. At step 164 a, masterplatform 70, which may be under software program control or equivalentmeans, is directed by master platform administrator 124 to update theentry corresponding to messaging platform 16 in master global routingtable 72 to reflect a DEACTIVATED operational status.

[0083] At step 164 b, master platform 70 sends an UPDATE message to eachof its assigned messaging platforms on messaging network 10. The UPDATEmessage includes the entry corresponding to messaging platform 16 thatreflects an DEACTIVATED operational status in master global routingtable 72.

[0084] In an alternative embodiment of the present invention, through amicroprocessor system running under program control or an equivalentdevice, master platform 70 may be configured to update automatically theentry corresponding to messaging platform 16 in master global routingtable 72 to reflect a DEACTIVATED operational status when messagingplatform does not respond as described above. This helps minimize theneed for any intervening action by master platform administrator 124, ifdesired.

[0085] At step 164 c, upon receiving the UPDATE message, each messagingplatform updates their global routing tables at the entry correspondingto messaging platform 16 to reflect a DEACTIVATED operational status.

[0086]FIG. 6B is a block diagram showing the activation of a messagingplatform in accordance with a preferred embodiment of the presentinvention.

[0087] Activating a messaging platform is similar to the steps outlinedimmediately above. At step 166 a, master platform 70 updates the entrycorresponding to messaging platform 16 in master global routing table 72to reflect an in-operation status, as shown in FIG. 6B.

[0088] At step 166 b, master platform 70 also sends an UPDATE message toeach of its assigned messaging platforms on messaging network 10. TheUPDATE message includes the entry corresponding to messaging platform 16that reflects an in-operation status in master global routing table 72.

[0089] At step 166 c, upon receiving the UPDATE message, each messagingplatform updates their global routing tables at the entry correspondingto messaging platform 16 to reflect an in-operation status.

[0090] Deleting a Messaging Platform

[0091]FIG. 6C is a block diagram showing the deletion of a messagingplatform in accordance with a preferred embodiment of the presentinvention.

[0092] As shown in FIGS. 1 and 6C, deleting a messaging platform such asmessaging platform 16 includes the following steps.

[0093] At step 168 a, master platform 70 deletes the entry correspondingto messaging platform 16 from master global routing table 72.

[0094] At step 168 b, the master platform updates the global routingtables of all messaging platforms that are to remain on the network (andwhich are assigned to the master platform) by sending a DELETE messageto each of its assigned messaging platforms on messaging network 10.

[0095] As presently contemplated, a DELETE message includes at least onemessaging platform entry that was deleted from master global routingtable 72 by master platform 70. The messaging platform entry is used bymessaging platforms to determine which entry in their global routingtables to delete.

[0096] At step 168 c, each messaging platform updates their globalrouting tables by deleting the entry corresponding to messaging platform16 using the messaging platform entry received from the DELETE message.

[0097] Tokens

[0098] Referring to FIG. 1, every network message delivery whichincludes using: 1) a switched network which forms the backbone formessaging network 10 such as switched backbone 18; 2) a network whichimposes an outside use fee such as telephone network 22; and 3) adestination messaging platform such as messaging platform 16 used tocomplete the messaging transaction, will have a delivery cost. Forexample, an owner of destination messaging platform in San Francisco,Calif., may incur a telephone transmission charge for transmitting a faxoriginating from a messaging platform in Hong Kong, China to a recipientin San Jose, California. In order to minimize the complexity that wouldresult if every independent owner of a messaging platform had tocontract with every other independent owner of a messaging platform inorder to deliver a message within a certain service area, the presentinvention imposes a cost for each network message delivery.

[0099] The cost for each network message delivery is measured in tokens.As described above, each messaging platform added to messaging network10 begins with a token pool having an initial amount of tokens. Eachowner of a messaging platform is charged for the cost of the tokens.Each time a network message delivery is initiated, the originatingmessaging platform debits a selected number of tokens from its tokenpool, while each time an inbound network message delivery occurs, aselected number of tokens are credited to the token pool held by atarget messaging platform. Each messaging platform performs the debitingand crediting functions under software control or equivalent means.

[0100] Replenishing Tokens

[0101] If the entire token pool held by a messaging platform falls belowa selected threshold amount such as when the token pool may soon bedepleted or is depleted, the pool is replenished centrally by using itsassigned master platform to provide additional tokens. Depletion of theentire pool of tokens for a given messaging platform ceases all networkmessage deliveries by that messaging platform until its token pool isreplenished. A microprocessor running under program control orequivalent device in the messaging platform determines whether it mayrequest delivery of a user message via the messaging network. The tokenpool may be replenished by purchasing additional tokens through arequest for replenishment to its assigned master platform or by gainingtokens from future inbound network message deliveries.

[0102] Upon a request for replenishment, the master platform sends anINFO message to the corresponding messaging platform which updates thetoken pool of that messaging platform. It is presently contemplated thatan owner of a new messaging platform purchases an initial token poolamount at the time the new messaging platform is added to the network.Additional tokens may then be purchased for replenishing any depletedamounts.

[0103] As presently contemplated, an INFO message includes a commandtype and the node ID and password (if applicable) of the sendingmessaging platform. For example, the INFO message command type mayinclude a token update command and a value for specifying areplenishment amount. The receiving messaging platform interprets anINFO message having a command type of token update by updating its tokenpool by the value specified in the command type.

[0104] Master Platform Post Office Feature

[0105] The present invention may also include a post office function forhandling a message that is intended for a message platform that is in anon-operational state (target messaging platform) such as a messagingplatform having a dial-up connection that is not within its operationschedule. The message is routed to a master platform which stores themessage. The master platform delivers the message to the targetmessaging platform when the master platform determines that the targetmessaging platform has an in-operation status.

[0106] For example, referring to FIG. 7, a messaging platform such asmessaging platform 170 may have a dial-up connection 172 to messagingnetwork 174 via its switched backbone such as the Internet 176. Sincedial-up connection 172 may not be continuous, messages sent betweenmessaging platform 170 and Internet 176 may be delayed. For example,messaging platform 178 may send a delivery-confirmed status message 180to messaging platform 170 to confirm delivery of a user message 182 sentfrom messaging platform 170. If messaging platform 170 has adisconnected dial-up connection 172, delivery-confirmed confirmingstatus message 180 will not arrive until dial-up connection 172 isre-established, which would be attempted during the operational perioddefined for messaging platform 170. Also, messaging platform 178 willnot receive a confirming message from messaging platform 170 thatdelivery-confirmed status message 180 has been received until dial-upconnection 172 has been established. Consequently, a status messageintended for a messaging platform having a non-operational status at thetime of delivery is instead routed to master platform 184 by themessaging platform that was requested to deliver a user message to alocal area such as messaging platform 178.

[0107] Messaging platform 178 determines whether messaging platform 170can receive the delivery-confirmed status message 180 by referring toglobal routing table 192. If the messaging platform entry in globalrouting table 192 indicates the inability of messaging platform 170 toreceive delivery-confirmed status message 180, messaging platform 178routes delivery-confirmed status message 180 to master platform 184. Theinability to receive status messages may be indicated, for example, byan operation schedule that shows a messaging platform is not within itsoperation window such as its daily and/or hourly operation period.

[0108] When master platform 184 receives confirming message 180 frommessaging platform 178, it stores confirming message 180 in a memorystore location 186 corresponding to messaging platform 170 (mailboxslot) and tags confirming message 180 for delivery the next timemessaging platform 170 is scheduled to re-connect. Master platform 184determines the appropriate time to deliver the reply message byreferencing messaging platform entry 188 corresponding to messagingplatform 170 in master global routing table 190.

[0109] Unlike a messaging platform having a dial-up connection or aconnection that has been interrupted, a messaging platform having adedicated connection receives status messages directly from the replyingmessaging platform such as messaging platform 178 in FIG. 7. Replyingmessaging platform 178 distinguishes between messaging platforms havinga dedicated or dial-up connections by referencing global routing table192.

[0110] As an alternative embodiment, a status message 194 may be sentdirectly by messaging platform 178 to the messaging platform 170 as anemail. However, if dial-up connection 172 has not yet beenre-established, status message 194 will not be delivered to messagingplatform 170 but will be held by the service provider 196 until dial-upconnection 172 is re-established. Unlike in the first embodiment, thisapproach does not specifically provide for a confirmation of receipt bymessaging platform 170 since service provider 196 may not provide aconfirmation of receipt of status message 194 by messaging platform 170once dial-up connection 172 has been re-established.

[0111] Information Delivery

[0112] Referring to FIGS. 7 and 8, the above described post officefeature may be enhanced to include delivering information 198 from atleast one information source 200 outside of messaging network 174 to amailbox 202 provided by messaging platform 204. Messaging platform 204has been configured to provide mailbox 202 which corresponds to asubscriber 205.

[0113] At step 206 a, subscriber 205 logs on to messaging platform 204to subscribe to an information delivery service provided by themessaging network. Logging on to messaging platform 204 may beaccomplished through a telephone 206 since messaging platform 204 isconfigured to provide a telephone interface capable of interpretingsubscriber-entered information made through a DTMF generator such asthrough a telephone keypad. To ensure proper information delivery,subscriber 205 is prompted for a mail box ID and/or password foridentification purposes.

[0114] At step 206 b, subscriber 205 provides service information 208 byselecting an information type 209, a delivery period 210 that defineshow often information type 208 is to be delivered, and a delivery format211. Service information 208 is provided through a service menu that ispresented to subscriber 205 by messaging platform 204. The service menuprovides a list of available services that messaging platform 204 hasbeen configured to provide to its supported users. One of the serviceslisted may include the information delivery service discussed herein.The service menu may also include additional services that are discussedin the present invention as well as services discussed in the multimediamessaging invention, which is incorporated herein by reference. Once theinformation delivery service is chosen, subscriber 205 is presented witha sub-menu that lists the information types that the messaging networkhas been configured to provide under that service.

[0115] For example, the sub-menu lists information types such as stocks,sports, and weather that may be selected by subscriber 205 through atelephone keypad (or equivalent DTMF generator). The button depressedreflects the position of the information type selected in the sub-menu,i.e, depressing a “1” chooses an information type of stocks, whiledepressing a “2” chooses an information type of sports. For aninformation type of stocks, messaging platform 204 also promptssubscriber 205 to enter a stock symbol using the telephone keypad in themanner outlined in the multimedia messaging invention, which isincorporated herein by reference.

[0116] Besides providing an information type 209 selection, subscriber205 is also prompted for a delivery period 210, and delivery format 211which are entered using the telephone keypad. In accordance with apresent embodiment of the present invention, delivery format 211includes an email, fax, or voice format.

[0117] At step 206 c, after step 206 b is complete, messaging platform204 contacts its assigned master platform such as master platform 184 bysending a SUBSCRIBE request to master platform 184. In response, masterplatform 184 requests service from information source 200 by providingservice information 208 received from subscriber 205. In addition,master platform 184 creates a storage location that corresponds tosubscriber 205 in a memory store 186 for holding any informationreceived from information source 200 that matches service information208 entered by subscriber 205 in step 206 b.

[0118] The SUBSCRIBE request includes a command type, a node IDcorresponding to messaging platform 204, a mailbox ID corresponding tosubscriber 205, and a password (if applicable). For example, thesubscribe request may include a command type that instructs masterplatform 184 to request that information source 200 provide theinformation sought in service information 208 that was chosen bysubscriber 205 in step 206 b.

[0119] At step 206 d, if service information 208 includes an emaildelivery format 211, step 206 e is performed. Otherwise step 206 f isperformed. At step 206 e, messaging platform converts any informationreceived from information source 200 that corresponds to serviceinformation 208 entered by subscriber 205 into a message having an emailformat and delivers the message to mailbox 204 which corresponds tosubscriber 205.

[0120] At step 206 f, if subscribing messaging platform 204 has anin-operation status, such as when it has a viable connection to theswitched backbone 176, step 206 g is performed. At step 206 g, anyinformation received from source 200 that corresponds to thesubscription information requested is forwarded to messaging platform204 by master platform 184.

[0121] If at step 206 f, subscribing messaging platform 204 has anon-operational status, step 206 h is performed. Through amicroprocessor system running under program control or equivalent devicemaster platform performs the following steps. At step 206 h, masterplatform stores any information received from source 200 in memory store186. Master platform 184 does not send the stored information to acorresponding subscriber's messaging platform 204 until master platform184 determines that messaging platform 204 has an in-operation status.For example, master platform 184 may refer to its master global routingtable to find a messaging platform entry that defines the profile formessaging platform 204 to determine whether messaging platform 204 hasan in-operation status based on the operation schedule listed inmessaging platform entry.

[0122] In an alternative embodiment, the present invention may use amaster platform 212 dedicated solely for the handling messagesoriginating from information sources outside the messaging network suchas from information source 214. Master platform 212 may be configured toreceive information through any of its network interfaces such asthrough its switched backbone interface 176 or through an interfacesupporting a dedicated connection to information source 214.

[0123] At step 206 i, the information received by master platform 184 isreceived by messaging platform 204 which converts the information tohave delivery format 210 prior to delivery.

[0124] At step 206 j, messaging platform 204 delivers the information tomailbox 202, which corresponds to subscriber 205, using delivery format210.

[0125] While illustrative embodiments and applications of this inventionhave been shown and described, it would be apparent to those skilled inthe art that many more modifications than have been mentioned above arepossible without departing from the inventive concepts set forth herein.The invention, therefore, is not to be limited except in the spirit ofthe appended claims.

What is claimed is:
 1. A method for managing messaging platforms on amessaging network, the method comprising the steps of: maintaining amessaging platform profile for a messaging platform on the messagingnetwork in a master profile table, said messaging platform profileincluding a host ID, an area of operation, an operational status, and atoken pool; storing a version of said master profile table in a globalprofile table held by each messaging platform on the messaging network;monitoring a messaging platform on the messaging network; updating saidmaster profile table in response to said step of monitoring; updatingsaid global profile table held by each messaging platform in response tosaid step of updating said master profile table, ensuring versionconsistency between said master profile table and each of said globalprofile tables; and using said operational status to determine whether amessaging platform may request delivery of a user message via themessaging network at an area of operation supported by a remotemessaging platform.
 2. The method in claim 1 , further including a stepof providing a new messaging platform on the messaging network with aninitial token pool amount.
 3. The method in claim 2 , further includinga step of deducting a number of tokens from said token pool held by anoriginating messaging platform, said originating messaging platformrequesting delivery of a user message which requires delivery by aremote messaging platform at an area of operation not supported by saidoriginating messaging platform.
 4. The method in claim 2 , furtherincluding a step of incrementing by a number of tokens said token poolheld by a messaging platform, wherein said messaging platform has beenrequested by an originating messaging platform to deliver a usermessage.
 5. The method in claim 2 , wherein said initial token poolamount differs between at least two messaging platforms on the messagingnetwork.
 6. The method in claim 2 , further including a step ofreplenishing a messaging platform on the messaging network with aspecified number of tokens when said token pool falls below a selectedthreshold.
 7. The method in claim 1 , further including a step ofreplenishing a messaging platform on the messaging network with aspecified number of tokens upon request by said messaging platform.
 8. Amethod for maintaining a messaging network having a master platform andat least one messaging platform, the master platform having a masterglobal routing table and each messaging platform having a global routingtable, the master global routing table and each global routing tableeach holding a messaging platform entry for each messaging platform onthe messaging network, each messaging platform entry having a host ID,an area of operation, an operational status, and a token pool, themethod comprising the steps of: responding to each messaging platform onthe messaging network that sends a HELLO message to the master platform,said HELLO message sent by each messaging platform at a selectedinterval which is defined in the messaging platform entry correspondingto each messaging platform; sending a QUERY message to a messagingplatform on the messaging network that fails to send a HELLO message tothe master platform within said selected interval; updating a messagingplatform entry of said messaging platform in the master global routingtable and the global routing table of each messaging platform on themessaging network, if said messaging platform fails to respond to saidQUERY message, said step of updating setting an operational statuswithin said messaging platform entry to indicate a disabled status; andusing said operational status of a remote messaging platform todetermine whether said messaging platform may send a user message usingthe messaging network to said remote messaging platform for delivery toan area of operation supported by said remote messaging platform.
 9. Themethod of claim 8 , further including the steps of: providing the tokenpool of each messaging platform with an initial amount of tokens;debiting a debit amount from the token pool of a messaging platform thatrequests delivery of a user message at an area of operation supported bya remote messaging platform; and incrementing a credit amount to thetoken pool of said remote messaging platform in response to the deliveryof said user message within said area of operation by said remotemessaging platform.
 10. The method of claim 9 , further including a stepof updating a messaging platform entry of a messaging platform to have adisabled operation status in response to said messaging platform havinga token pool amount that falls below a selected threshold.
 11. A methodfor managing a messaging network having at least one messaging platformwith each messaging platform having a global profile table, the methodcomprising the steps of: responding to an add request by creating a newmessaging platform profile, said new messaging platform profilecorresponding to a new messaging platform on the messaging network andincluding a host ID, an area of operation, an operational status, and atoken pool which correspond to said new messaging platform profile;including said new messaging platform profile in a master profile table,said master profile table having a messaging platform profile for eachmessaging platform existing on the messaging network; providing anetwork address of a master platform to said new messaging platform;providing said master profile table to said new messaging platform whensaid new messaging platform establishes a network connection; andupdating the global profile table in each existing messaging platform onthe messaging network to include said new messaging platform profile.12. The method of claim 11 , further including the steps of: determiningwhether a messaging platform on the messaging network has anon-operational status by using a messaging platform profile whichcorresponds to the messaging platform; routing a status message to amaster platform in response to said messaging platform having saidnon-operational status; storing said status message in a storagelocation corresponding to said messaging platform, said storage locationprovided by said master platform; and delivering said status messagestored in said storage location to the messaging platform when saidmessaging platform has an in-operation status.
 13. The method of claim12 , further including a step of sending a confirmation message to anoriginating messaging platform which sent said status message when saidmaster platform delivers said status message to said messaging platformhaving said dial-up connection.
 14. The method of claim 11 , furtherincluding a step of responding to a messaging platform on the messagingnetwork that sends a HELLO message, said HELLO message sent by saidmessaging platform at a selected interval which is defined in themessaging platform profile of said messaging platform.
 15. The method ofclaim 14 , further including a step of sending a QUERY message to amessaging platform on the messaging network that fails to send a HELLOmessage within said selected interval.
 16. The method of claim 15 ,further including a step of updating a messaging platform profile of amessaging platform that fails to respond to a QUERY message, said stepof updating setting an operational status within said platform profileto indicate a disabled status.
 17. The method of claim 11 , furtherincluding a step of updating a messaging platform profile of a messagingplatform to have a disabled operation status in response to saidmessaging platform having a token pool amount that falls below aselected threshold.
 18. The method of claim 11 , further including astep of deleting a messaging platform profile of a messaging platform inresponse to a DELETE message.
 19. A method of routing a message to amessaging platform on a messaging network, the method comprising thesteps of: determining whether the messaging platform has anon-operational status by using a messaging platform profile whichcorresponds to the messaging platform; routing said message to a masterplatform in response to the messaging platform having saidnon-operational status; storing said message in a storage locationcorresponding to the messaging platform, said storage location providedby said master platform; and delivering said message stored in saidstorage location to the messaging platform when the messaging platformhas an in-operation status.
 20. The method of claim 19 , wherein saidstep of determining includes using an operation schedule defined for themessaging platform in said messaging platform profile.
 21. The method ofclaim 19 , wherein said messaging platform profile is stored in a globalprofile table, said global profile table being available to everymessaging platform on the messaging network.
 22. A method for providinginformation to a subscriber on a messaging system, the method comprisingthe steps of: providing a mailbox ID and service information to amessaging platform, said mailbox ID corresponding to a subscriberserviced by said messaging platform and said service informationincluding an information type, a delivery period, and a delivery format;sending a request to a master platform in response to said serviceinformation, said master platform responding to said request byrequesting information from an information source, said informationcorresponding to said service information; sending information receivedfrom said information source to said messaging platform; convertinginformation received from said information source into a delivery formatcorresponding to said delivery format selected in said step of providingservice information; and providing said information to a subscriber whensaid subscriber accesses a mailbox corresponding to said mailbox ID. 23.The method in claim 22 , further including the step of maintaining amaster profile table, said master profile table having a messagingplatform profile for each messaging platform established on themessaging network, said messaging platform profile including a host ID,an area of operation, an operation schedule, and a token pool.
 24. Themethod in claim 22 , wherein said delivery format includes a faxdelivery format.
 25. The method in claim 22 , wherein said deliveryformat includes a voice delivery format.
 26. The method in claim 22 ,wherein said delivery format includes an email format.
 27. The method ofclaim 22 , wherein said master platform forwards said informationreceived from said information source to said messaging platform onlywhen said messaging platform has an in-operation status.
 28. The methodof claim 27 , where said in-operation status is based on said operationschedule defined for said messaging platform.
 29. The method of claim 22, wherein said master platform delays sending said information receivedfrom said information source to said messaging platform when saidmessaging platform has a non-operational status.
 30. The method of claim29 , wherein said non-operational status is obtained when said tokenpool falls below a selected threshold.
 31. The method of claim 22 ,where said master platform converts said information received from saidinformation source into an email format and sends said email formattedinformation to a mailbox supported by a messaging platform thatcorresponds to said mailbox ID, if an email format has been chosen assaid delivery format.
 32. A system for managing messaging platforms on amessaging network, the system comprising: means for maintaining amessaging platform profile for each messaging platform on the messagingnetwork in a master profile table, said messaging profile including ahost ID, an area of operation, an operational status, and a token pool,said means for maintaining also maintain a current version of saidmaster profile table in a global profile table held by each messagingplatform on the messaging network; means for monitoring each messagingplatform on the messaging network; means for updating said masterprofile table responsive to said means for monitoring; means forupdating said global profile table held by each messaging platformresponsive to said means for updating said master profile table,ensuring version consistency between said master profile table and eachof said global profile tables; and means for using said operationalstatus to determine whether a messaging platform may request delivery ofa user message via the messaging network at an area of operationsupported by a remote messaging platform.
 33. The system in claim 32 ,further including means for providing a new messaging platform on themessaging network with an initial token pool amount.
 34. The system inclaim 33 , further including means for deducting a number of tokens fromsaid token pool held by an originating messaging platform, saidoriginating messaging platform requesting delivery of a user messagewhich requires delivery by a remote messaging platform at an area ofoperation not supported by said originating messaging platform.
 35. Thesystem in claim 33 , further including means for incrementing by anumber of tokens said token pool held by a messaging platform, whereinsaid messaging platform has been requested by an originating messagingplatform to deliver a user message.
 36. The system in claim 33 , whereinsaid initial token pool amount differs between at least two messagingplatforms on the messaging network.
 37. The system in claim 32 , furtherincluding means for replenishing a messaging platform on the messagingnetwork with a specified number of tokens when said messaging platformfalls below a selected token pool amount.
 38. The system in claim 32 ,further including means for replenishing a messaging platform on themessaging network with a specified number of tokens upon request by saidmessaging platform.
 39. A system for maintaining a messaging networkhaving at least one messaging platform, the system comprising: a masterplatform having a master global routing table which holds a messagingplatform entry for each messaging platform on the messaging network,each messaging platform entry having a host ID, an area of operation, anoperational status, and a token pool; a global routing table for eachmessaging platform, wherein said global routing table holds a messagingplatform entry for each messaging platform on the messaging network,each messaging platform entry having a host ID, an area of operation, anoperational status, and a token pool; wherein said master platformresponds to each messaging platform on the messaging network that sendsa HELLO message to said master platform, said HELLO message sent by eachmessaging platform at a selected interval which is defined in themessaging platform entry corresponding to each messaging platform;wherein said master platform sends a QUERY message to a messagingplatform on the messaging network that fails to send a HELLO message tothe master platform within said selected interval; wherein said masterplatform updates said operational status of said messaging platformentry to include a disabled status, said messaging platform entrycorresponding to said messaging platform in said master global routingtable and said global routing table of each messaging platform on themessaging network, if said messaging platform fails to respond to saidQUERY message; and wherein a messaging platform on the network checkssaid operational status of a remote messaging platform to determinewhether said messaging platform may send a user message using themessaging network to remote messaging platform for to delivery to anarea of operation supported by said remote messaging platform.
 40. Thesystem of claim 39 , wherein said master platform provides said tokenpool of each messaging platform with an initial amount of tokens; saidmaster platform debits a debit amount from a token pool of anoriginating messaging platform that requests delivery of a user messageat an area of operation supported by a remote messaging platform; andsaid master platform increments a credit amount to a token pool of saidremote messaging platform in response to the delivery of said usermessage within said area of operation by said remote messaging platform.41. The system of claim 40 , wherein said master platform updates amessaging platform profile of a messaging platform to have a disabledoperation status in response to said messaging platform having a tokenpool amount that falls below a selected threshold.
 42. A system formaintaining a messaging network having at least one messaging platform,each messaging platform having a messaging platform profile, the systemcomprising: a master platform which creates a new messaging platformprofile in response to an add request, said new messaging platformprofile corresponding to a new messaging platform and including a hostID, an area of operation, an operational status, and a token pool;wherein said master platform includes said new messaging platformprofile in a master profile table, said master profile table alsoincluding a messaging platform profile for each messaging platformexisting on the messaging network; wherein said master platform providessaid master profile table to said new messaging platform when said newmessaging platform establishes a network connection; and wherein saidmaster platform updates each global profile table corresponding to eachexisting messaging platforms on the messaging network to include saidnew messaging platform profile.
 43. The system of claim 42 , whereinsaid master platform responds to each messaging platform on themessaging network that sends a HELLO message, said HELLO message sent byeach messaging platform at a selected interval which is defined in themessaging platform profile of each messaging platform.
 44. The system ofclaim 43 , wherein said master platform sends a QUERY message to amessaging platform on the messaging network that fails to send a HELLOmessage within said selected interval.
 45. The system of claim 44 ,wherein said master platform updates a messaging platform profile of amessaging platform that fails to respond to a QUERY message to indicatea disabled status.
 46. The system of claim 42 , wherein said masterplatform updates a messaging platform profile of a messaging platform tohave a disabled operation status in response to a messaging platformhaving a token pool amount that falls below a selected threshold. 47.The system of claim 42 , further including means for deleting amessaging platform profile of a messaging platform, said means fordeleting responsive to a DELETE message.
 48. The system of claim 42 ,wherein said master platform includes means for receiving a statusmessage destined for a messaging platform having a dial-up connection tothe messaging network when said dial-up connection is not established onthe messaging network, said master platform further including means fordelivering said status message to said messaging platform when saidoperational period indicates said messaging platform has established atemporary dial-up connection to the messaging network.
 49. The system ofclaim 48 , wherein said master platform sends a confirmation message toan originating messaging platform that sent said status message whensaid master platform delivers said status message to said messagingplatform.
 50. A system for delivering a status message to a messagingplatform, the system comprising: a first messaging platform; a secondmessaging platform having a global profile table which includes amessaging platform profile for said first messaging platform, the firstmessaging platform having a global profile table which includes amessaging platform profile for said second messaging platform, the firstmessaging platform having means for determining the operational statusof said second messaging platform using said messaging platform profilecorresponding to said second messaging platform; a master platformhaving a master profile table which includes a messaging platformprofile for said first messaging platform and said second messagingplatform, said master platform having means for determining anoperational status of said first and second messaging platforms; andwherein said first messaging platform routes the status message to saidmaster platform in response to said second messaging platform having anon-operational status, said master platform having a storage locationfor storing the status message and means for delivering the statusmessage to said second messaging platform, said means for deliveringresponsive to said means for determining said operational status of saidsecond messaging platform.
 51. The system in claim 50 , wherein saidmaster platform maintains content consistency between said masterprofile table and said global profile tables of said first messagingplatform and said second messaging platform.
 52. A system for deliveringinformation to a subscriber on a messaging system, the systemcomprising: a messaging platform having means for receiving a mailbox IDand service information from a subscriber and means for requesting froma master platform information corresponding to said service information,said master platform having means for communicating with an informationsource, said means for communicating responsive to said means forrequesting by requesting information corresponding to said serviceinformation from said information source; wherein said master platformresponds to any information received from said information source bysending said information to said messaging platform; and wherein saidmessaging platform converts said information to have a delivery formatcorresponding to a delivery format selected by said subscriber, saidmessaging platform having means for providing said information in saiddelivery format to said subscriber when said subscriber accesses amailbox corresponding to said mailbox ID.
 53. The system in claim 52 ,wherein said service information includes an information type, adelivery period, and a delivery format.
 54. The system in claim 52 ,wherein said delivery format includes a voice delivery format.
 55. Thesystem in claim 52 , wherein said delivery format includes an emailformat.
 56. The system in claim 52 , wherein said delivery formatincludes a fax format.
 57. The system of claim 52 , wherein said masterplatform forwards said information received from said information sourceto said messaging platform only when said messaging platform has anin-operation status.
 58. The system of claim 57 , wherein saidin-operation status is based on said operation schedule defined for saidmessaging platform.
 59. The system of claim 52 , wherein said masterplatform delays sending said information received from said informationsource to said messaging platform when said messaging platform has anon-operational status.
 60. The system of claim 59 , wherein saidnon-operational status is obtained when said token pool falls below aselected threshold.
 61. The system of claim 52 , where said masterplatform converts said information received from said information sourceinto an email format and sends said email formatted information to amailbox supported by a messaging platform that corresponds to saidmailbox ID, if an email format has been chosen as said delivery format.